Skip to content

fix: ensure same version is reported by extension and MCP sever#93

Open
haroonc wants to merge 4 commits intomainfrom
fix-version
Open

fix: ensure same version is reported by extension and MCP sever#93
haroonc wants to merge 4 commits intomainfrom
fix-version

Conversation

@haroonc
Copy link
Contributor

@haroonc haroonc commented Mar 15, 2026

Currently the version reported by the MCP server does not match with the version from release.
Updated workflows to consolidate version string

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines the version management process for the extension and its MCP server component. By centralizing the version definition in a single root file and automating its injection during the build, it ensures consistency across all components and simplifies future version updates, preventing discrepancies between reported versions.

Highlights

  • Centralized Versioning: Introduced a new VERSION file at the root of the repository to consolidate the project's version string, providing a single source of truth.
  • Automated Version Injection: Modified the build.sh script to read the version from the new VERSION file and inject it into the Go binary during compilation using ldflags, ensuring the MCP server reports the correct version.
  • Removed Redundant Version File: Eliminated devops-mcp-server/version.txt as its purpose is now served by the centralized VERSION file.
  • Updated Development Versions: Adjusted hardcoded version strings in devops-mcp-server/server.go and gemini-extension.json to reflect development states, relying on the build process for release versions.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • VERSION
    • Added a new file to define the consolidated project version.
  • build.sh
    • Updated to read the version from the new VERSION file and pass it as a build flag to the Go compiler.
  • devops-mcp-server/server.go
    • Modified the version variable to a development default, expecting the build process to override it.
  • devops-mcp-server/version.txt
    • Removed the dedicated version file for the MCP server.
  • gemini-extension.json
    • Updated the extension's version to a development placeholder.
Ignored Files
  • Ignored by pattern: .github/workflows/** (2)
    • .github/workflows/nightly-release.yml
    • .github/workflows/release.yml
Activity
  • No human activity has been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request aims to unify the versioning for the extension and the MCP server by using a single VERSION file. While the build script is correctly updated to inject this version into the server binary, the gemini-extension.json manifest is changed to a hardcoded development version, which conflicts with the version in the VERSION file. This defeats the primary goal of the PR. I've provided a critical comment to fix this inconsistency. Additionally, I've suggested a minor improvement to the build script for more robust version handling.

haroonc and others added 3 commits March 15, 2026 15:33
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant